home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
EnigmA Amiga Run 1998 July
/
EnigmA AMIGA RUN 29 (1998)(G.R. Edizioni)(IT)[!][issue 1998-07 & 08].iso
/
earkit
/
browser
/
alynx
/
orig
/
00readme
next >
Wrap
Text File
|
1998-05-24
|
8KB
|
200 lines
Lynx2-4-FM:
===========
This archive contains the Lynx source set with bug fixes and
enhancements as implemented at the Worcester Foundation. Read the
CHANGES file for a description of the modifications through the date
of this archive. Thereafter, check the CHANGES file in:
http://www.wfeb.edu/dir/lynx
or: gopher://gopher.wfeb.edu/11/_fileserv/_lynx
for any further bug fixes or enhancements.
This distribution contains all the files for building Lynx with
all flavors of Unix and on VMS with VAXC, DECC or GNUC on VAXen or AXPen,
and the associated documentation and example files.
This distribution is mirrored in:
ftp://ftp.hhs.dk/fote_mirror
It is not an "official" Lynx distribution, but simply the code
we are using at the Worcester Foundation. Our code through 08-Jun-1995
was archived at UKans as Lynx2-4. Read the appended messages from Michael
Grobe, Jeff Porter, and Craig Lavender.
Contact Craig (lavender@lark.cc.ukans.edu) if you have any questions
concerning plans at UKans for Lynx development.
Report bugs and contribute patches to:
lynx-dev@ukanaix.cc.ukans.edu.
Fote
=========================================================================
Foteos Macrides Worcester Foundation
MACRIDES@SCI.WFEB.EDU 222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
From: IN%"lynx-dev@ukanaix.cc.ukans.edu" 28-OCT-1994
Subj: RE: Is Lynx dead? ^^^^^^^^^^^
KU has absolutely no plans to "kill lynx".
lynx is alive and well, recovering from a period of partial catatonia.
we have hired a full-time programmer and 2 part-time students to
keep lynx alive and upgrade it as the web evolves. the full-time
person is jeff porter, who started this month and is busy acclimating.
jeff and i both attended the developer's conference in chicago.
the issue of whether or not we have to license is not determined
yet. i continute to want to avoid licensing, and i continue to face
funding problems, so licensing continues to hold some allure.
i hope that helps clarify what is going on.
:michael grobe
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Michael Grobe
Manager Director
Distributed Computing Support Kansas Research and Education
Academic Computing Services Network (KANREN)
The University of Kansas
Lawrence, KS 66045
(913) 864-0452
grobe@ukanaix.cc.ukans.edu
==============================================================================
From: IN%"lynx-dev@ukanaix.cc.ukans.edu" 24-FEB-1995
Subj: RE: lynx development (longish) ^^^^^^^^^^^
> > From: d-lewart@uiuc.edu (Daniel S. Lewart)
> > Lynx-Dev,
> >
> > 5) Is `lynx' development based at UKans or at WFEB now?
Thank you for the input and the questions. I believe the first four
comments have been addressed, but please notify me if they require
further discussion. I would like to address the last question you asked.
Lynx development is, and always has been, based at the University of
Kansas. Before I took the lynx development position here, just about
everyone involved in lynx development left to engage in other pursuits.
Fortunately, many of the people on this list have been involved with lynx
development, some from nearly the beginning of the project. Many of you
continue to provide specific fixes and new features. Lynx would not be
the program that it is without the great work that the people on this
list have contributed.
I think that there comes a time in any large project to take a serious
look at the way the code has "grown" over the years and do some
re-engineering. It's important to add new features and provide quick
fixes, but it is also important to strengthen the foundation. This will
improve everything built on top of it. The downside is that it takes
longer for this kind of development to reach the users.
Rest assured that lynx development is ongoing at KU and there is no
reason to believe that it will not continue. In fact, we have plans to
increase the staff time devoted to it. Now is a good time to look beyond
simple fixes and do some more fundamental development. I believe that
the efforts made to improve the structure of the code and it operation
will make future development much more efficient and enjoyable.
As always, your comments are welcome. I am very interested in ways you
think that lynx can be improved. There is no need to limit your ideas to
things that would be easy to accomplish. I want to make lynx a better
tool, and sometimes that requires larger shifts in capabilities.
Thanks,
Jeff
--
Jeff Porter - Distributed Applications Programmer
Computing Services - University of Kansas
email: jporter@stat1.cc.ukans.edu
phone: 913-864-0460
==============================================================================
From: IN%"lynx-dev@ukanaix.cc.ukans.edu" 9-JUN-1995
Subj: lynx 2.4 ^^^^^^^^^^
Hello,
I have placed a new version of lynx on ftp2.cc.ukans.edu, called
lynx2.4 to avoid confusion. This version contains all of the
enhancements that Foteos added and we will be adding our own
enhancements to this version as well. Foteos has done a great job of
enhancing lynx and coordinating other people's enhancements. I'm sure
the entire lynx community joins me in thanking him for his
contributions.
As people have patches and changes to lynx I will incorporate them
into lynx and put them up on our server. This way it should be easier
to get the most up to date copy of lynx. If you have any modifications
that you would like to add please send them to me and I will include
them. When modifications come in that we need to test we will first put
them into a lynx2-xbeta package and place that on ftp2 (for the brave)
and leave a lynx2-x package (for the slightly less brave).
I haven't yet put compiled binaries up, but hopefully later this
afternoon you will be able to grab those as well.
P.S. This is separate from the lynx3.0 work that is being done.
Lynx2.4 is the same lynx we know and love. We plan on making
lynx3.0 use the libwww 3.0 library.
Later
--
Jeff Porter - Distributed Applications Programmer &
distributed-way-too-thin eecs grad student
Academic Computing Services, University of Kansas
email: jporter@ukans.edu phone: 913-864-0460
==============================================================================
From: IN%"lynx-dev@ukanaix.cc.ukans.edu" 27-JUL-1995 19:56:55.77
^^^^^^^^^^^
Hello,
In an attempt to get my Master's Degree before I am old and decrepit I
will be leaving the Computer Center and becoming a full-time graduate
student. Craig Lavender and Ravi Kolli, under the direction of Michael
Grobe, will therefore be taking the responsibility for KU's contribution
to lynx development. Craig is now the list owner for lynx-dev as well and
any problems with the list should be directed to him.
--
Jeff Porter - Distributed Applications Programmer &
distributed-way-too-thin eecs grad student
Academic Computing Services, University of Kansas
email: jporter@ukans.edu phone: 913-864-0460
==============================================================================
From: IN%"lynx-dev@ukanaix.cc.ukans.edu" 21-JUL-1995 20:50:37.42
^^^^^^^^^^^
[...]
I hope to have KU's lynx2-4-* keep up with the lynx2-4-FM distribution.
[...]
--
Craig A. Lavender Work Phone: (913) 864-0436
Student Programmer/Consultant Email: lavender@ukans.edu
ACS User Services WWW: http://lark.cc.ukans.edu/~lavender
University of Kansas
==============================================================================